Skip to content

Improve handling of unexpected values for upcomingMaintenance #4119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

mr0re1
Copy link
Collaborator

@mr0re1 mr0re1 commented May 13, 2025

  • Log VM name for cases where maintenance can not be handled;
  • Be aware about maintenance type (can be different from SCHEDULED);

@mr0re1 mr0re1 requested review from samskillman and a team as code owners May 13, 2025 21:20
@mr0re1 mr0re1 added the release-chore To not include into release notes label May 13, 2025
gemini-code-assist[bot]

This comment was marked as resolved.

gemini-code-assist[bot]

This comment was marked as resolved.

@tpdownes tpdownes assigned mr0re1 and unassigned tpdownes May 14, 2025
* Log VM name for cases where maintenance can not be handled;
* Be aware about maintenance `type` (can be different from `SCHEDULED`);
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-chore To not include into release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants